Skip to content

docs(roadmap): C-first sufficiency targets and approved v2 Issue template - #40

Merged
xLagerFeuer merged 2 commits into
mainfrom
docs/c-first-roadmap-priority-v2-issue-template-20261118
Nov 17, 2026
Merged

xLagerFeuer merged 2 commits into
mainfrom
docs/c-first-roadmap-priority-v2-issue-template-20261118

Conversation

@xLagerFeuer

Copy link
Copy Markdown
Member

Scope

Apply the owner's approved v2 capability integration roadmap Issue template, and make useful, evidence-backed C sufficiency the explicit default target of upstream roadmap for functions without confirmed A or C.

This is a roadmap-procedure and template change, not a Paperclip product implementation, a VSM Index reassessment, an external maintainer Issue or an automatic fork Issue publication.

Behavior changes

  1. C-target first: identify relevant functions without accepted and current-source-supported A/A(P) or C/C(P). For —, unresolved ? and eligible P, seek the smallest source-native change set that would be sufficient for a first-party developer-composable C path when there is genuine user value. Resolve ? and current-source conflicts first; preserve legitimate P authority.
  2. A is not C: an already A/A(P) function does not need new mandatory C work, even though the two classifications are not logical synonyms. Already C/C(P) functions do not need duplicate constructors. No autonomy-grade ladder.
  3. Priority: P0 = a material, source-backed C sufficiency target; P1 = dependencies needed for that target, which may execute first; P2 = optional modes/refinements. The choice is based on operator benefit, reusable Issues/PRs, measurable acceptance, complexity and cost—not the lowest Index grade.
  4. Proof obligation: show historical Index state vs observed original HEAD, shipped/source-native behavior vs open Issues/PRs, minimum full set of existing and proposed changes, constructor/rights/closure and testable sufficiency. Plans cannot claim shipped or Index-verified C. No qualified path => explicit NEEDS_EVIDENCE/NO_USEFUL_CHANGE.
  5. Adopt v2: replace the prior 7-section generic fork Issue skeleton with the approved 8-section capability integration Issue template, including mandatory target matrix, priority/dependency matrix and C sufficiency contract. Keep the external architecture Issue template separate.

Files and checks

  • PROTOCOL.md: default target, priority and receipt gate.
  • docs/CAPABILITY_ROADMAP.md: target-first procedure and receipt.
  • templates/FORK_CAPABILITY_ROADMAP_ISSUE.md: v2, Opensiro spelling.
  • tests/test_fork_roadmap_issue_template.py: v2 sections and classification/priority/consent invariants.
  • CHANGELOG.md: unreleased entry.

No version/Release change, product branch edit or public GitHub Issue. No edit of the existing Paperclip/Browser Harness historical roadmap examples in this PR.

Prioritize first-party C construction for functions without evidenced C or A, exclude already-autonomous functions from mandatory C engineering, preserve legitimate parent rights, separate P0 targets from P1 prerequisites and P2 optional modes. Adopt eight-section target/dependency/sufficiency Issue template with tests.
@xLagerFeuer
xLagerFeuer merged commit e18aacc into main Nov 17, 2026
1 check passed
@xLagerFeuer
xLagerFeuer deleted the docs/c-first-roadmap-priority-v2-issue-template-20261118 branch November 17, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant